home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
gt_power
/
gtrprd11.zip
/
MAKE_NET.DOC
< prev
next >
Wrap
Text File
|
1989-06-01
|
6KB
|
119 lines
MAKE_NET - Create/Update The USERNET.DAT File.
Version 1.00
Copyright 1989 by Scott Swaine
DISCLAIMER:
----------
(Insert your favorite disclaimer here...or use the one included)
You may copy and distribute this software freely in it's original
unmodified form and such the no monetary action is involved.
I make no claims that this program will work in the manner desired by
the consumer, other than it did what *I* wanted it to do, in my
environment. I will not be responsible for any losses resulting,
either directly or indirectly, from the use or misuse of this
software.
DESCRIPTION:
-----------
This is another of my "Short & Sweet" series that I've been making
lately for this GT to ProDoor 'kit'. This one serves practically NO
purpose whatsoever, other than to satisfy my curiosity about
something. So I'm including it anyway, just to pump up the file size
of this package. I knew you'd like that! (snicker)
What this does is create the PCBoard 14.0 version of the USERNET.DAT
file, which is used on PCBoard systems to log what node (on a multi-
node system) is doing what. Like, for instance, one node may be
downloading a file, while another is out a door, and a third is
'chatting' with a fourth. That kind of thing. There's three
versions of this file, for the three differeny 'sizes' of multi-node
PCBoard systems. There's a three-node version, a 9-node version and
an 'unlimited', or 99-node, version. This file can handle any size,
but I didn't go so far as to make it limit the size if you tell it
node 12 (on a 9-node system) is doing such 'n such. It will probably
extend the file to meet that size. So for the sake of the poor li'l
program, don't make it do something it doesn't know better than NOT
to do.
USAGE:
-----
To use it, enter it's name on the command line and put three
parameters on that line with it. The combination may vary, so here's
what's allowed... Entering it's name without parameters gives a help
screen showing some valid parameter combinations.
First, let me say that the second parameter is ALWAYS the path and
name for the USERNET.DAT file.
If the first param. is "INIT", the USERNET.DAT file will be created.
The third param. is a number, in this case the number of records to
put into this file when initializing it.
The second option is to insert an entry for a node into this file.
Specify the name/location of a PCBoard 14.0 version PCBOARD.SYS file,
as created by my MAKE_SYS utility, as the first parameter. The third
should be the node number of the node being inserted. Remember, it
should be within the limits of the size for the file you initialized.
The third option is to 'logout' from this file, and you do this by
specifying the word "LOGOUT" as the first parameter, and the node
number as the third. The entry is then removed from the file. It's
pretty simple, if you ask me.
NETWORKING:
----------
If you should happen to find a PCBoard 14 door that actually uses
this file for something, like ProDoor, then the use for this may
become apparent, if even in a limited way, since the current version
of ProDoor (as of this writing) doesn't do more than look at this
file to tell you the status of other nodes. But this may be used for
something bigger and better, someday. The entries I put in here are
whether or not the node being entered is 'available' or 'unavailable'
for chatting (node chatting, that is). This is an 'A' or a 'U' code,
as specified in the USERNET.DAT file.
Starting with version 1.15 of MAKE_SYS, I am including a new command
line parameter to carry this idea through to it, which tells it to
put the proper node number and the 'A' or 'U' code into the
PCBOARD.SYS file. I may be premature with this at this time, but
it's sorta in preparation for the up and coming LAN-compatible,
multi-node GT Power 15.00. Maybe this will help future purchasers of
that fine BBS program to run multi-node compatible doors.
MAKE_NET uses file sharing functions for opening and accessing the
USERNET.DAT file. If you use it on a network, it SHOULD work if more
than one node is accessing the file...but I have yet to really test
this part of it. The time it takes to access the file is so short,
it's quite unlikely that there will be enough time for two or more
node to access it. And even at that, they should only access, via
reading and writing, ONE record of this file, depending on the node
number.
"...and that's the name of THAT tune."
Scott Swaine, Sysop
Console Command Headquarters
Node 1: (805) 968-5094
Node 2: (805) 968-9411
Node 3: (805) 968-0734
24 hours/day
300/1200/2400/9600 baud, 8-N-1
GT Network net/node 054/000
CompuServe ID: 72057,1542